CALL FOR TOOL DEMONSTRATIONS
Fifth International Conference on
Generative Programming and Component Engineering (GPCE'06)
October 22-26, 2006
Portland, Oregon
(co-located with OOPSLA'06)
Sponsored by ACM SIGPLAN, in cooperation with ACM SIGSOFT.
GPCE'06 proceedings published by ACM Press.
Program Chairs
- Douglas Schmidt, Vanderbilt University
- Todd Veldhuizen, Indiana University
Program chairs can be contacted at
gpce06-chairs-l@mailman.rice.edu
for issues concerning tool demonstrations
Important Dates
Overview
The conference on Generative Programming and Component Engineering
offers practitioners and tool-developers an opportunity to give an
in-depth technical demonstration of products, tools, techniques or
approaches supporting program generation, domain-specific modeling,
generative programming, template meta-programming,
aspect-oriented software development, model-driven architecture,
component generation, and other related topics.
GPCE tool demonstrations typically show how tools are applied in real
world scenarios, for example, by considering a small case-study. We
explicitly invite proposals from both industry as well as academia.
Demonstrations will be selected on their technical content, practical
or academic relevance, and feasibility of the proposed demonstration.
While we encourage proposals for the demonstration of commercial tools, we expect the presentation to address technical issues. Product marketing is inappropriate for this forum. If there are concerns with regard to the appropriateness of a demonstration or tool, feel free to contact
gpce06-chairs-l@mailman.rice.edu.
Organizational Issues
A demonstration session lasts 45 minutes, and should be centered
around a technical exposition of the tool, but the demonstrators
should provide time for questions from the public, either during the
session or at the end.
Demonstration proposals, written according to the guidelines outlined
below, should be submitted by
May 5, 2006, 23:59, Apia time (tentative).
Electronic submission will be required.
Proponents will be notified of acceptance by
June 28, 2005 (tentative).
Demonstration proposals will be evaluated by the Program Committee and
will compete with technical papers for time slots in the Conference
Program.
It is the responsibility of the proponent to meet the hardware and software requirements needed to run a demonstration (ideally it should run on the presenter's laptop). The conference organization will provide only a data projector, an overhead projector and wireless connection.
Presenters of accepted demonstrations must provide a two-page summary description to be published on the website and handed out at the conference.
Proposal Guidelines
A proposal for demonstration be submitted electronically in
PDF format and should contain the following information:
- A demonstration title
- Name, organization, email, address, and phone number of the contact person
- Names and affiliations of the other presenters
- A description (max 400 words) addressing the following issues:
- Problems addressed
- Relevance to Generative Programming or Component Engineering
- Uniqueness of design and implementation,
- Underlying implementation techniques and technologies used
- A description of what the audience will see and how the
demonstration will be run
- A URL of a web site with additional information, if available
Program Committee
Program Chairs:
Program Committee Members:
- Giuseppe Attardi (University of Pisa, Italy)
- Elisa Baniassad (Chinese University of Hong Kong, China)
- Don Batory (University of Texas at Austin, USA)
- Ira Baxter (Semantic Designs, USA)
- Shigeru Chiba (Tokyo Institute of Technology, Japan)
- Charles Consel (INRIA/LaBRI, France)
- Krzysztof Czarnecki (University of Waterloo, Canada)
- Aniruddha Gokhale (Vanderbilt University, USA)
- Jeff Gray (U. of Alabama Birmingham, USA)
- George Heineman (Worcester Polytechnic Institute, USA)
- Zhenjiang Hu (University of Tokyo, Japan)
- H.-Arno Jacobsen (University of Toronto, Canada)
- Oleg Kiselyov (FNMOC, USA)
- Fabio Kon (University of São Paulo, Brazil)
- Karl Lieberherr (Northeastern University, USA)
- Joe Loyall (BBN Technologies, USA)
- Mira Mezini (Darmstadt University of Technology, Germany)
- Torben Æ. Mogensen (DIKU, Denmark)
- Emir Pasalic (Rice University, USA)
- Calton Pu (Georgia Tech, USA)
- Tim Sheard (Portland State University, USA)
- Yannis Smaragdakis (Georgia Tech, USA)
- Michael Stal (Siemens, Germany)
- Peri Tarr (IBM TJ Watson, USA)
- Peter Thiemann (Freiburg University, Germany)
- Eelco Visser (Utrecht University, The Netherlands)
For More Information
For additional information, clarification, or questions, please feel
free to e-mail (
gpce06-chairs-l@mailman.rice.edu)
Important Dates
* There will be no pre-submission.
*
Submission:
May 5, 2006, 23:59, Apia time (tentative)
extended
* Notification:
June 28, 2005 (tentative)
Scope
Generative and component approaches are revolutionizing
software development similar to how automation and components
revolutionized manufacturing.
Generative Programming
(developing programs that synthesize other programs),
Component Engineering
(raising the level of modularization and analysis in
application design), and
Domain-Specific Languages (elevating
program specifications to compact domain-specific notations that are
easier to write, maintain, and analyze) are key technologies for
automating program development.
GPCE provides a venue for researchers and practitioners interested in
foundational techniques for enhancing the productivity, quality, and
time-to-market in software development that stems from deploying
standard componentry and automating program generation. In addition
to exploring cutting-edge techniques for developing generative and
component-based software, our goal is to foster further
cross-fertilization between the software engineering research
community and the programming languages community.
Submissions
10 pages in
SIGPLAN proceedings style
(sigplanconf.cls) reporting research results and/or
experience related to the topics above (PC co-chairs can advise on
appropriateness). We particularly encourage original high-quality
reports on applying GPCE technologies to real-world problems, relating
ideas and concepts from several topics, or bridging the gap between
theory and practice.
To submit a paper, go to the
electronic submission page.
Please note that GPCE 2006 is using a double-blind reviewing process. Authors
should read carefully the instructions on the electronic submission page.
Topics
GPCE seeks contributions in software engineering and in
programming languages related (but not limited) to:
* Generative programming
* Reuse, meta-programming, partial evaluation, multi-stage and multi-level languages, and step-wise refinement
* Semantics, type systems, symbolic computation, linking and explicit substitution, in-lining and macros, templates, and program transformation
* Runtime code generation, compilation, active libraries, synthesis from specifications, development methods, generation of non-code artifacts, formal methods, and reflection
* Generative techniques for
* Product-line architectures
* Distributed, real-time and embedded systems
* Model-driven development and architecture
* Component-based software engineering
* Reuse, distributed platforms and middleware, distributed systems, evolution, patterns, development methods, deployment and configuration techniques, and formal methods
* Integration of generative and component-based approaches
* Domain engineering and domain analysis
* Domain-specific languages (DSLs) including visual and UML-based DSLs
* Separation of concerns
* Aspect-oriented and feature-oriented programming,
* Intentional programming and multi-dimensional separation of concerns
* Industrial applications
Reports on applications of these techniques to real-world problems are especially encouraged, as are submissions that relate ideas and concepts from several of these topics, or bridge the gap between theory and practice. The program committee is happy to advise on the appropriateness of a particular subject.
General Chair
Stanislaw Jarzabek (National University of Singapore, Singapore)
Program Committee
Program Chairs:
Program Committee Members:
- Giuseppe Attardi (University of Pisa, Italy)
- Elisa Baniassad (Chinese University of Hong Kong, China)
- Don Batory (University of Texas at Austin, USA)
- Ira Baxter (Semantic Designs, USA)
- Shigeru Chiba (Tokyo Institute of Technology, Japan)
- Charles Consel (INRIA/LaBRI, France)
- Krzysztof Czarnecki (University of Waterloo, Canada)
- Aniruddha Gokhale (Vanderbilt University, USA)
- Jeff Gray (U. of Alabama Birmingham, USA)
- George Heineman (Worcester Polytechnic Institute, USA)
- Zhenjiang Hu (University of Tokyo, Japan)
- H.-Arno Jacobsen (University of Toronto, Canada)
- Oleg Kiselyov (FNMOC, USA)
- Fabio Kon (University of São Paulo, Brazil)
- Karl Lieberherr (Northeastern University, USA)
- Joe Loyall (BBN Technologies, USA)
- Mira Mezini (Darmstadt University of Technology, Germany)
- Torben Æ. Mogensen (DIKU, Denmark)
- Emir Pasalic (Rice University, USA)
- Calton Pu (Georgia Tech, USA)
- Tim Sheard (Portland State University, USA)
- Yannis Smaragdakis (Georgia Tech, USA)
- Michael Stal (Siemens, Germany)
- Peri Tarr (IBM TJ Watson, USA)
- Peter Thiemann (Freiburg University, Germany)
- Eelco Visser (Utrecht University, The Netherlands)
Workshops/Tutorials chairs:
*
Christa Schwanninger (Siemens, Germany)
*
Arno Jacobsen (University of Toronto, Canada)
Publicity chair:
*
Emir Pasalic (Rice University, USA)
Steering Committee
- Don Batory (University of Texas at Austin, USA)
- Krzysztof Czarnecki (University of Waterloo, Canada)
- Ulrich Eisenecker (University of Leipzig, Germany)
- Stanislaw Jarzabek (National University of Singapore, Singapore)
- Eugenio Moggi (University of Genoa, Italy)
- Greg Morrisett (Harvard University, USA)
- Frank Pfenning (Carnegie Mellon University, USA)
- Tim Sheard (Portland State University, USA)
- Yannis Smaragdakis (Georgia Tech, USA)
- Walid Taha (Rice University, USA)
For More Information
For additional information, clarification, or questions please feel free to contact the Program Committee Co-chairs (
Gpce06-chairs-l@mailman.rice.edu).
Check for latest news at
http://gpce06.gpce.org
.
GPCE Tutorials and Workshops
GPCE Tutorials, extending over a half or full day, give a deeper or broader insight than conventional lectures.
GPCE Workshops
provide intensive collaborative environments,
where generative and component technologists meet to discuss and
resolve challenging problems in the field.
Tutorial and workshop proposals are due
Mar 18, 2006.
Poster Chair
Important Dates
- Poster proposal submission:
- Notification of acceptance:
- Conference:
Overview
Posters at GPCE provide an excellent forum for authors to present their work in an informal and interactive setting. Posters are ideal for presenting speculative, late-breaking results or for giving an introduction to interesting, innovative work. They are intended to provide authors and interested participants with the ability to connect with each other and to engage in discussions about the work. Posters provide authors with a unique opportunity to make their work highly visible during the conference. Therefore, authors of other GPCE technical submissions are encouraged to also submit a poster about their work. Posters will be on display during the entire conference.
Successful posters are carefully designed to convey technical details. They should also have a strong visual impact that attracts the attention of attendees as they stroll past the displays, either during the interactive poster session or at other times during the conference. The goal is to develop a poster that encourages and facilitates small groups of individuals interested in a technical area to gather and interact. The interactive poster session is held early in the conference, to promote continued discussion among interested parties.
Submission Format
The poster itself or the preliminary graphic layout must be submitted as a PDF file. A Poster proposal consists of:
- a 50 word or less short abstract that summarizes the content of the poster
- a set of keywords describing the technical area of the work
- a two-page extended abstract, suitable for inclusion in the GPCE 2004 Conference CD
- the poster itself, or a preliminary graphic layout of the poster (please review the poster content guidelines)
The preliminary graphic layout should consist of 1 to 3 pages that sketch the layout for an ?.?? meter (wide) by ?.?? meter (high) bulletin board. Please use 10 point or larger font in the preliminary layout, and 12 point or larger in the final poster, so that it is readable. Once you have submitted your proposal, you will receive confirmation by e-mail that your proposal has been received and is complete.
Please send poster proposals to the GPCE 2004 Posters Chair TBA to arrive no later than TBA. For additional information, clarifications, questions, or special requirements, please also contact .
Submission Guidelines
Posters cover the same interest areas as the Technical Papers, Demonstrations, and Workshops, and provide an opportunity to present work in a highly visual and interactive format:
- Conference participants who are giving technology demonstrations should consider presenting posters that contain overviews of their demonstrations, both to attract additional attendance at demonstrations and to increase the visibility of their tools.
- Technology providers can showcase their tools and technologies with posters.
- The poster session provides graduate students with an outstanding forum in which to present and discuss their PhD work.
- Research laboratories and projects can introduce themselves and their key efforts to the community by presenting posters.
- Workshop organizers and/or attendees may present posters that summarize results from GPCE 2003 workshops. The poster session provides workshop participants a means of communicating their key results to the rest of the community.
- Authors of work that is presented in the GPCE technical program can obtain even more benefit by presenting their work in a poster as well. The poster session provides them the opportunity to engage in more personal one-on-one discussions.
Suggestions for other key topic areas are also encouraged.
Poster authors are required to attend the scheduled interactive poster session, staying with their poster so that they can discuss their work with conference attendees. Some poster authors also post an informal schedule along with their poster, listing times when they plan to be available for discussion later on during the conference. Others leave sign-up sheets for interested viewers to obtain further information. All posters will have an associated "message board", on which viewers can post comments, ideas, and questions and on which poster authors will be able to post responses.
Posters are advertised in the Final Program, and authors' two-page extended abstracts will appear in the GPCE Conference CD, which will be distributed at to all GPCE'04 attendees. Attendees will be able to learn more about individual posters before or after visiting the exhibit.
For More Information
For additional information, clarification, or questions please feel free to contact the Poster Chair
Industrial Track Chair
Important Dates
- Practitioner report submission:
- Notification of acceptance:
- Program posted on the conference website:
- Conference:
Overview
Practitioner reports explore how concepts that sound good on paper work on real projects. They are a valuable means of communicating experiences, especially at the "bleeding edge" of technology. Many GPCE attendees want to find out what it is like to adopt new tools and development techniques; use new engineering methods; create domain-specific languages, generators, architectures and components; develop applications using the new technologies, etc. Expectations, beliefs, and hopes can be validated, or dashed, by the experience that is reported. GPCE attendees want objective reports with supporting evidence for any claims made. And they particularly want reports that discuss both benefits and drawbacks of the approaches used.
We seek for reports in two categories:
- Project reports will describe successfully completed projects that applied technologies within the scope of GPCE'04.
- Experience reports will focus on a particular aspect of technology usage and practice, or describe broad project experiences.
The report must contain a take-home-message for your readers; something they can learn and apply to their own work. Plain "how we did it" reports should be avoided.
Presented project and experience reports will take part in the audience vote for the GPCE'04 Best Contribution Awards.
Submission Process
You are invited to submit a four to ten page project report presenting your successful project or experience report describing your experience applying technologies within the scope of GPCE'04. The submission must include a short abstract suitable for inclusion in the Advance Program should it be accepted. If your report is accepted for presentation at GPCE, you will be expected to develop and present a 20 minute talk that will be followed by discussion. The written reports will be published at gpce.org. The submission, including full contact information (name, mailing address, telephone and fax numbers, and electronic mail address), should be submitted as a PDF, OpenOffice, or a Microsoft Word file to the Industrial Track Chair. The report submissions will be reviewed separately from technical paper submissions by a practitioner report committee. The submission should clearly state whether it should be reviewed as a project or experience report.
For More Information
For additional information, clarification, or questions please feel free to contact the Industrial Track Chair.
Tutorial Chairs
- Christa Schwanninger, Siemens AG
- Hans-Arno Jacobson, University of Toronto
Tutorial chairs can be contacted at
tutorials06@gpce.org
Important Dates
- Preliminary proposal submission deadline: Mar 18, 2006
- Preliminary date for notification of acceptance: May 01, 2006
Tutorials that have less than 10 early registrants will be at risk of cancellation.
Overview
Proposals for high-quality tutorials in all areas of generative programming
and component-based development, from academic research to industrial
applications, are solicited. Tutorial levels may be introductory, intermediate,
or advanced.
A tutorial's purpose is to give a deeper insight into an area than a
conventional lecture. Tutorials extend over a half or a full day. This gives
the speaker the possibility to select a proper length for their tutorial.
The topic of a tutorial can come from a truly broad spectrum. Any interesting
theme included but not restricted to the following topic list is welcome:
- Generative programming
- Reuse, meta-programming, partial evaluation, multi-stage and multi-level languages, step-wise refinement
- Semantics, type systems, symbolic computation, linking and explicit substitution, in-lining and macros, templates, program transformation
- Runtime code generation, compilation, active libraries, synthesis from specifications, development methods, generation of non-code artifacts, formal methods, reflection
- Generative techniques for
- Product lines and architectures
- Embedded systems
- Model-driven architecture
- Component-based software engineering
- Reuse, distributed platforms, distributed systems, evolution, analysis and design patterns, development methods, formal methods
- Integration of generative and component-based approaches
- Domain engineering and domain analysis
- Domain-specific languages (DSLs) including visual and UML-based DSLs
- Separation of concerns
- Aspect-oriented programming and feature-oriented programming,
- Intentional programming and multi-dimensional separation of concerns
- Industrial applications
However, you
should keep in mind that a tutorial must be expected to attract a reasonable
number of participants. This is most likely the case if the topic is new or
relevant to a broad community. If you have deep experience in a GPCE topic area,
from which others could benefit, please consider submitting a proposal.
Submission Format
Proposals must contain all information requested in the
SubmissionFormat template.
What should a tutorial look like?
In case your tutorial is accepted, the
TutorialGuidelines offer suggestions for preparing and
presenting your tutorial.
Submission Process
Electronic submission of proposals must be sent to
tutorials06@gpce.org.
Proposals must be submitted no later than
Mar 18, 2006.
The proposals received will be reviewed by the Tutorial Committee to ensure
a high quality and appropriate mix for the conference. The Tutorial Chairs will
work toward a diverse program that attracts a large interest among the broad
segments within GPCE.
For More Information
For additional information, clarification, or questions please feel free to contact the Tutorial Chairs (
tutorials06@gpce.org)
Workshop Chairs
- Christa Schanninger, Siemens AG
- Hans-Arno Jacobosn, University of Toronto
Workshop chairs can be contacted at
workshop06@gpce.org
Important Dates
Workshop proposal schedule:
- Preliminary submission deadline for workshop proposals: Mar 18, 2006
- Preliminary date for notification of workshop acceptance: May 01, 2006
This call is for workshop organizers; a later call will
occur for workshop contributions.
Overview
GPCE workshops provide intensive collaborative environments where generative
and component technology researchers and practitioners meet to discuss and
solve challenging problems facing the field.
We encourage proposals for innovative, well-focused workshops on a broad
spectrum of component engineering and generative programming topics. All topics
related to the theme of the conference are potential candidates for workshops.
Workshops typically fall into the following categories:
- A workshop may address a specific sub-area of generative and component
technology in depth.
- A workshop may cover areas that cross the borders of several sub areas.
Workshops that cross the borders of the formal and the applied areas is
one example.
- A workshop may also cross the border to other technologies or software engineering fields, e.g. development processes.
- A workshop may focus on the application and deployment of generative
and/or component technology in areas such as telecommunications, mobile
computing or real-time systems. Workshops reporting on industrial
experiences are particularly welcome.
Workshop topics are by no means limited to the categories mentioned above.
However, in each case, the proposed area is supposed to have enough impetus
to yield new results that can be considered important and worth more detailed
investigation.
Submission Format
Workshop proposals should be sent in ASCII or PDF format to the workshop
chairs and should consist of the following four parts:
1. Cover Page
- Name of the proposed workshop.
- Names and addresses of the organizers.
- Primary contact.
- Intended number of participants.
- Requested Audio/Video equipment.
2. Abstract
- Why is the proposed workshop relevant to GPCE? The abstract should
provide a short overview of the rationale for the workshop and the
major topics. In particular, statements about the review process and
ways to ensure creativity during the workshop would be appreciated.
- The abstract should preferably not exceed 200 words.
3. Call for Participation
- A preliminary version of the Call for Participation that the organizers
must prepare if the workshop is accepted.
- Should provide a brief overview of the proposed workshop including a
description of the goals of the workshops and the work practices.
- May repeat some of the statements made on the abstract page, but should
be targeted specifically to potential workshop participants.
4. Organizers Bio and Past Events
- Short biography of each organizer.
- References to similar workshops organized at previous conferences,
including the number of participants.
If a workshop is accepted, the organizers will be requested to prepare
a WWW page that will contain the latest information about the workshop.
The web pages of each workshop will be linked to the GPCE workshop web
site.
Each workshop must have at least two organizers, preferably from
different organizations.
Please keep complete submissions to under four pages.
Recommendations
1. Workshop organizers should foster the creative potential that is
tentatively present in a workshop.
2. Remember that a workshop is NOT a conference!
3. The success of a workshop depends greatly on the results generated on-site.
4. A number of interrelated issues should be taken into account in order to
provide a good framework for such on-site creativity.
5. Presentation selection
- Quality should obviously be the primary criterion for selecting the
presentations.
- However, in order for a workshop to be productive, consider also having
presentations on some new, controversial topics to spark discussion.
Workshop attendance will be manage via the GPCE registration form.
Workshop organizers and presenters are required to register to the workshop.
Submission Process
Electronic submission of proposals must be sent to
workshops06@gpce.org.
Proposals must be submitted no later than
Mar 18, 2006, BUT EARLIER IS BETTER, as
it allows for a more satisfactory coordination between workshop proposals.
The submitted proposals will be reviewed collectively by the Workshop
Committee to determine a high quality and appropriate mix for the conference.
For More Information
For additional information, clarification, or questions please feel free to
contact the Workshop Chairs (
workshops06@gpce.org).